{{/*
Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.
*/}}
<table class="configuration table table-bordered">
    <thead>
        <tr>
            <th class="text-left" style="width: 20%">Key</th>
            <th class="text-left" style="width: 15%">Default</th>
            <th class="text-left" style="width: 10%">Type</th>
            <th class="text-left" style="width: 55%">Description</th>
        </tr>
    </thead>
    <tbody>
        <tr>
            <td><h5>auto-create</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to create underlying storage when reading and writing the table.</td>
        </tr>
        <tr>
            <td><h5>branch</h5></td>
            <td style="word-wrap: break-word;">"main"</td>
            <td>String</td>
            <td>Specify branch name.</td>
        </tr>
        <tr>
            <td><h5>bucket</h5></td>
            <td style="word-wrap: break-word;">-1</td>
            <td>Integer</td>
            <td>Bucket number for file store.<br />It should either be equal to -1 (dynamic bucket mode), or it must be greater than 0 (fixed bucket mode).</td>
        </tr>
        <tr>
            <td><h5>bucket-key</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Specify the paimon distribution policy. Data is assigned to each bucket according to the hash value of bucket-key.<br />If you specify multiple fields, delimiter is ','.<br />If not specified, the primary key will be used; if there is no primary key, the full row will be used.</td>
        </tr>
        <tr>
            <td><h5>cache-page-size</h5></td>
            <td style="word-wrap: break-word;">64 kb</td>
            <td>MemorySize</td>
            <td>Memory page size for caching.</td>
        </tr>
        <tr>
            <td><h5>changelog-producer</h5></td>
            <td style="word-wrap: break-word;">none</td>
            <td><p>Enum</p></td>
            <td>Whether to double write to a changelog file. This changelog file keeps the details of data changes, it can be read directly during stream reads. This can be applied to tables with primary keys. <br /><br />Possible values:<ul><li>"none": No changelog file.</li><li>"input": Double write to a changelog file when flushing memory table, the changelog is from input.</li><li>"full-compaction": Generate changelog files with each full compaction.</li><li>"lookup": Generate changelog files through 'lookup' before committing the data writing.</li></ul></td>
        </tr>
        <tr>
            <td><h5>changelog-producer.row-deduplicate</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to generate -U, +U changelog for the same record. This configuration is only valid for the changelog-producer is lookup or full-compaction.</td>
        </tr>
        <tr>
            <td><h5>changelog.num-retained.max</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>The maximum number of completed changelog to retain. Should be greater than or equal to the minimum number.</td>
        </tr>
        <tr>
            <td><h5>changelog.num-retained.min</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>The minimum number of completed changelog to retain. Should be greater than or equal to 1.</td>
        </tr>
        <tr>
            <td><h5>changelog.time-retained</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>The maximum time of completed changelog to retain.</td>
        </tr>
        <tr>
            <td><h5>commit.callback.#.param</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Parameter string for the constructor of class #. Callback class should parse the parameter by itself.</td>
        </tr>
        <tr>
            <td><h5>commit.callbacks</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>A list of commit callback classes to be called after a successful commit. Class names are connected with comma (example: com.test.CallbackA,com.sample.CallbackB).</td>
        </tr>
        <tr>
            <td><h5>commit.force-compact</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to force a compaction before commit.</td>
        </tr>
        <tr>
            <td><h5>commit.force-create-snapshot</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to force create snapshot on commit.</td>
        </tr>
        <tr>
            <td><h5>commit.user-prefix</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Specifies the commit user prefix.</td>
        </tr>
        <tr>
            <td><h5>compaction.max-size-amplification-percent</h5></td>
            <td style="word-wrap: break-word;">200</td>
            <td>Integer</td>
            <td>The size amplification is defined as the amount (in percentage) of additional storage needed to store a single byte of data in the merge tree for changelog mode table.</td>
        </tr>
        <tr>
            <td><h5>compaction.max.file-num</h5></td>
            <td style="word-wrap: break-word;">50</td>
            <td>Integer</td>
            <td>For file set [f_0,...,f_N], the maximum file number to trigger a compaction for append-only table, even if sum(size(f_i)) &lt; targetFileSize. This value avoids pending too much small files, which slows down the performance.</td>
        </tr>
        <tr>
            <td><h5>compaction.min.file-num</h5></td>
            <td style="word-wrap: break-word;">5</td>
            <td>Integer</td>
            <td>For file set [f_0,...,f_N], the minimum file number which satisfies sum(size(f_i)) &gt;= targetFileSize to trigger a compaction for append-only table. This value avoids almost-full-file to be compacted, which is not cost-effective.</td>
        </tr>
        <tr>
            <td><h5>compaction.optimization-interval</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>Implying how often to perform an optimization compaction, this configuration is used to ensure the query timeliness of the read-optimized system table.</td>
        </tr>
        <tr>
            <td><h5>compaction.size-ratio</h5></td>
            <td style="word-wrap: break-word;">1</td>
            <td>Integer</td>
            <td>Percentage flexibility while comparing sorted run size for changelog mode table. If the candidate sorted run(s) size is 1% smaller than the next sorted run's size, then include next sorted run into this candidate set.</td>
        </tr>
        <tr>
            <td><h5>consumer-id</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Consumer id for recording the offset of consumption in the storage.</td>
        </tr>
        <tr>
            <td><h5>consumer.expiration-time</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>The expiration interval of consumer files. A consumer file will be expired if it's lifetime after last modification is over this value.</td>
        </tr>
        <tr>
            <td><h5>consumer.ignore-progress</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to ignore consumer progress for the newly started job.</td>
        </tr>
        <tr>
            <td><h5>consumer.mode</h5></td>
            <td style="word-wrap: break-word;">exactly-once</td>
            <td><p>Enum</p></td>
            <td>Specify the consumer consistency mode for table.<br /><br />Possible values:<ul><li>"exactly-once": Readers consume data at snapshot granularity, and strictly ensure that the snapshot-id recorded in the consumer is the snapshot-id + 1 that all readers have exactly consumed.</li><li>"at-least-once": Each reader consumes snapshots at a different rate, and the snapshot with the slowest consumption progress among all readers will be recorded in the consumer.</li></ul></td>
        </tr>
        <tr>
            <td><h5>continuous.discovery-interval</h5></td>
            <td style="word-wrap: break-word;">10 s</td>
            <td>Duration</td>
            <td>The discovery interval of continuous reading.</td>
        </tr>
        <tr>
            <td><h5>cross-partition-upsert.bootstrap-parallelism</h5></td>
            <td style="word-wrap: break-word;">10</td>
            <td>Integer</td>
            <td>The parallelism for bootstrap in a single task for cross partition upsert.</td>
        </tr>
        <tr>
            <td><h5>cross-partition-upsert.index-ttl</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>The TTL in rocksdb index for cross partition upsert (primary keys not contain all partition fields), this can avoid maintaining too many indexes and lead to worse and worse performance, but please note that this may also cause data duplication.</td>
        </tr>
        <tr>
            <td><h5>delete.force-produce-changelog</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Force produce changelog in delete sql, or you can use 'streaming-read-overwrite' to read changelog from overwrite commit.</td>
        </tr>
        <tr>
            <td><h5>deletion-vector.index-file.target-size</h5></td>
            <td style="word-wrap: break-word;">2 mb</td>
            <td>MemorySize</td>
            <td>The target size of deletion vector index file.</td>
        </tr>
        <tr>
            <td><h5>deletion-vectors.enabled</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to enable deletion vectors mode. In this mode, index files containing deletion vectors are generated when data is written, which marks the data for deletion. During read operations, by applying these index files, merging can be avoided.</td>
        </tr>
        <tr>
            <td><h5>dynamic-bucket.assigner-parallelism</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>Parallelism of assigner operator for dynamic bucket mode, it is related to the number of initialized bucket, too small will lead to insufficient processing speed of assigner.</td>
        </tr>
        <tr>
            <td><h5>dynamic-bucket.initial-buckets</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>Initial buckets for a partition in assigner operator for dynamic bucket mode.</td>
        </tr>
        <tr>
            <td><h5>dynamic-bucket.target-row-num</h5></td>
            <td style="word-wrap: break-word;">2000000</td>
            <td>Long</td>
            <td>If the bucket is -1, for primary key table, is dynamic bucket mode, this option controls the target row number for one bucket.</td>
        </tr>
        <tr>
            <td><h5>dynamic-partition-overwrite</h5></td>
            <td style="word-wrap: break-word;">true</td>
            <td>Boolean</td>
            <td>Whether only overwrite dynamic partition when overwriting a partitioned table with dynamic partition columns. Works only when the table has partition keys.</td>
        </tr>
        <tr>
            <td><h5>fields.default-aggregate-function</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Default aggregate function of all fields for partial-update and aggregate merge function.</td>
        </tr>
        <tr>
            <td><h5>file-index.in-manifest-threshold</h5></td>
            <td style="word-wrap: break-word;">500 bytes</td>
            <td>MemorySize</td>
            <td>The threshold to store file index bytes in manifest.</td>
        </tr>
        <tr>
            <td><h5>file-index.read.enabled</h5></td>
            <td style="word-wrap: break-word;">true</td>
            <td>Boolean</td>
            <td>Whether enabled read file index.</td>
        </tr>
        <tr>
            <td><h5>file-reader-async-threshold</h5></td>
            <td style="word-wrap: break-word;">10 mb</td>
            <td>MemorySize</td>
            <td>The threshold for read file async.</td>
        </tr>
        <tr>
            <td><h5>file.block-size</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>MemorySize</td>
            <td>File block size of format, default value of orc stripe is 64 MB, and parquet row group is 128 MB.</td>
        </tr>
        <tr>
            <td><h5>file.compression</h5></td>
            <td style="word-wrap: break-word;">"zstd"</td>
            <td>String</td>
            <td>Default file compression. For faster read and write, it is recommended to use LZ4.</td>
        </tr>
        <tr>
            <td><h5>file.compression.per.level</h5></td>
            <td style="word-wrap: break-word;"></td>
            <td>Map</td>
            <td>Define different compression policies for different level, you can add the conf like this: 'file.compression.per.level' = '0:lz4,1:zstd'.</td>
        </tr>
        <tr>
            <td><h5>file.compression.zstd-level</h5></td>
            <td style="word-wrap: break-word;">1</td>
            <td>Integer</td>
            <td>Default file compression zstd level. For higher compression rates, it can be configured to 9, but the read and write speed will significantly decrease.</td>
        </tr>
        <tr>
            <td><h5>file.format</h5></td>
            <td style="word-wrap: break-word;">"orc"</td>
            <td>String</td>
            <td>Specify the message format of data files, currently orc, parquet and avro are supported.</td>
        </tr>
        <tr>
            <td><h5>file.format.per.level</h5></td>
            <td style="word-wrap: break-word;"></td>
            <td>Map</td>
            <td>Define different file format for different level, you can add the conf like this: 'file.format.per.level' = '0:avro,3:parquet', if the file format for level is not provided, the default format which set by `file.format` will be used.</td>
        </tr>
        <tr>
            <td><h5>full-compaction.delta-commits</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>Full compaction will be constantly triggered after delta commits.</td>
        </tr>
        <tr>
            <td><h5>ignore-delete</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to ignore delete records.</td>
        </tr>
        <tr>
            <td><h5>incremental-between</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Read incremental changes between start snapshot (exclusive) and end snapshot, for example, '5,10' means changes between snapshot 5 and snapshot 10.</td>
        </tr>
        <tr>
            <td><h5>incremental-between-scan-mode</h5></td>
            <td style="word-wrap: break-word;">auto</td>
            <td><p>Enum</p></td>
            <td>Scan kind when Read incremental changes between start snapshot (exclusive) and end snapshot. <br /><br />Possible values:<ul><li>"auto": Scan changelog files for the table which produces changelog files. Otherwise, scan newly changed files.</li><li>"delta": Scan newly changed files between snapshots.</li><li>"changelog": Scan changelog files between snapshots.</li></ul></td>
        </tr>
        <tr>
            <td><h5>incremental-between-timestamp</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Read incremental changes between start timestamp (exclusive) and end timestamp, for example, 't1,t2' means changes between timestamp t1 and timestamp t2.</td>
        </tr>
        <tr>
            <td><h5>local-merge-buffer-size</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>MemorySize</td>
            <td>Local merge will buffer and merge input records before they're shuffled by bucket and written into sink. The buffer will be flushed when it is full.
Mainly to resolve data skew on primary keys. We recommend starting with 64 mb when trying out this feature.</td>
        </tr>
        <tr>
            <td><h5>local-sort.max-num-file-handles</h5></td>
            <td style="word-wrap: break-word;">128</td>
            <td>Integer</td>
            <td>The maximal fan-in for external merge sort. It limits the number of file handles. If it is too small, may cause intermediate merging. But if it is too large, it will cause too many files opened at the same time, consume memory and lead to random reading.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache-file-retention</h5></td>
            <td style="word-wrap: break-word;">1 h</td>
            <td>Duration</td>
            <td>The cached files retention time for lookup. After the file expires, if there is a need for access, it will be re-read from the DFS to build an index on the local disk.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache-max-disk-size</h5></td>
            <td style="word-wrap: break-word;">infinite</td>
            <td>MemorySize</td>
            <td>Max disk size for lookup cache, you can use this option to limit the use of local disks.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache-max-memory-size</h5></td>
            <td style="word-wrap: break-word;">256 mb</td>
            <td>MemorySize</td>
            <td>Max memory size for lookup cache.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache-spill-compression</h5></td>
            <td style="word-wrap: break-word;">"lz4"</td>
            <td>String</td>
            <td>Spill compression for lookup cache, currently none, lz4, lzo and zstd are supported.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache.bloom.filter.enabled</h5></td>
            <td style="word-wrap: break-word;">true</td>
            <td>Boolean</td>
            <td>Whether to enable the bloom filter for lookup cache.</td>
        </tr>
        <tr>
            <td><h5>lookup.cache.bloom.filter.fpp</h5></td>
            <td style="word-wrap: break-word;">0.05</td>
            <td>Double</td>
            <td>Define the default false positive probability for lookup cache bloom filters.</td>
        </tr>
        <tr>
            <td><h5>lookup.hash-load-factor</h5></td>
            <td style="word-wrap: break-word;">0.75</td>
            <td>Float</td>
            <td>The index load factor for lookup.</td>
        </tr>
        <tr>
            <td><h5>manifest.compression</h5></td>
            <td style="word-wrap: break-word;">"zstd"</td>
            <td>String</td>
            <td>Default file compression for manifest.</td>
        </tr>
        <tr>
            <td><h5>manifest.format</h5></td>
            <td style="word-wrap: break-word;">"avro"</td>
            <td>String</td>
            <td>Specify the message format of manifest files.</td>
        </tr>
        <tr>
            <td><h5>manifest.full-compaction-threshold-size</h5></td>
            <td style="word-wrap: break-word;">16 mb</td>
            <td>MemorySize</td>
            <td>The size threshold for triggering full compaction of manifest.</td>
        </tr>
        <tr>
            <td><h5>manifest.merge-min-count</h5></td>
            <td style="word-wrap: break-word;">30</td>
            <td>Integer</td>
            <td>To avoid frequent manifest merges, this parameter specifies the minimum number of ManifestFileMeta to merge.</td>
        </tr>
        <tr>
            <td><h5>manifest.target-file-size</h5></td>
            <td style="word-wrap: break-word;">8 mb</td>
            <td>MemorySize</td>
            <td>Suggested file size of a manifest file.</td>
        </tr>
        <tr>
            <td><h5>merge-engine</h5></td>
            <td style="word-wrap: break-word;">deduplicate</td>
            <td><p>Enum</p></td>
            <td>Specify the merge engine for table with primary key.<br /><br />Possible values:<ul><li>"deduplicate": De-duplicate and keep the last row.</li><li>"partial-update": Partial update non-null fields.</li><li>"aggregation": Aggregate fields with same primary key.</li><li>"first-row": De-duplicate and keep the first row.</li></ul></td>
        </tr>
        <tr>
            <td><h5>metadata.stats-mode</h5></td>
            <td style="word-wrap: break-word;">"truncate(16)"</td>
            <td>String</td>
            <td>The mode of metadata stats collection. none, counts, truncate(16), full is available.<br /><ul><li>"none": means disable the metadata stats collection.</li></ul><ul><li>"counts" means only collect the null count.</li></ul><ul><li>"full": means collect the null count, min/max value.</li></ul><ul><li>"truncate(16)": means collect the null count, min/max value with truncated length of 16.</li></ul><ul><li>Field level stats mode can be specified by fields.{field_name}.stats-mode</li></ul></td>
        </tr>
        <tr>
            <td><h5>metastore.partitioned-table</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to create this table as a partitioned table in metastore.
For example, if you want to list all partitions of a Paimon table in Hive, you need to create this table as a partitioned table in Hive metastore.
This config option does not affect the default filesystem metastore.</td>
        </tr>
        <tr>
            <td><h5>metastore.tag-to-partition</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Whether to create this table as a partitioned table for mapping non-partitioned table tags in metastore. This allows the Hive engine to view this table in a partitioned table view and use partitioning field to read specific partitions (specific tags).</td>
        </tr>
        <tr>
            <td><h5>metastore.tag-to-partition.preview</h5></td>
            <td style="word-wrap: break-word;">none</td>
            <td><p>Enum</p></td>
            <td>Whether to preview tag of generated snapshots in metastore. This allows the Hive engine to query specific tag before creation.<br /><br />Possible values:<ul><li>"none": No automatically created tags.</li><li>"process-time": Based on the time of the machine, create TAG once the processing time passes period time plus delay.</li><li>"watermark": Based on the watermark of the input, create TAG once the watermark passes period time plus delay.</li><li>"batch": In the batch processing scenario, the tag corresponding to the current snapshot is generated after the task is completed.</li></ul></td>
        </tr>
        <tr>
            <td><h5>num-levels</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>Total level number, for example, there are 3 levels, including 0,1,2 levels.</td>
        </tr>
        <tr>
            <td><h5>num-sorted-run.compaction-trigger</h5></td>
            <td style="word-wrap: break-word;">5</td>
            <td>Integer</td>
            <td>The sorted run number to trigger compaction. Includes level0 files (one file one sorted run) and high-level runs (one level one sorted run).</td>
        </tr>
        <tr>
            <td><h5>num-sorted-run.stop-trigger</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>The number of sorted runs that trigger the stopping of writes, the default value is 'num-sorted-run.compaction-trigger' + 3.</td>
        </tr>
        <tr>
            <td><h5>page-size</h5></td>
            <td style="word-wrap: break-word;">64 kb</td>
            <td>MemorySize</td>
            <td>Memory page size.</td>
        </tr>
        <tr>
            <td><h5>parquet.enable.dictionary</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>Turn off the dictionary encoding for all fields in parquet.</td>
        </tr>
        <tr>
            <td><h5>partition</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Define partition by table options, cannot define partition on DDL and table options at the same time.</td>
        </tr>
        <tr>
            <td><h5>partition.default-name</h5></td>
            <td style="word-wrap: break-word;">"__DEFAULT_PARTITION__"</td>
            <td>String</td>
            <td>The default partition name in case the dynamic partition column value is null/empty string.</td>
        </tr>
        <tr>
            <td><h5>partition.expiration-check-interval</h5></td>
            <td style="word-wrap: break-word;">1 h</td>
            <td>Duration</td>
            <td>The check interval of partition expiration.</td>
        </tr>
        <tr>
            <td><h5>partition.expiration-time</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>The expiration interval of a partition. A partition will be expired if it‘s lifetime is over this value. Partition time is extracted from the partition value.</td>
        </tr>
        <tr>
            <td><h5>partition.timestamp-formatter</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>The formatter to format timestamp from string. It can be used with 'partition.timestamp-pattern' to create a formatter using the specified value.<ul><li>Default formatter is 'yyyy-MM-dd HH:mm:ss' and 'yyyy-MM-dd'.</li><li>Supports multiple partition fields like '$year-$month-$day $hour:00:00'.</li><li>The timestamp-formatter is compatible with Java's DateTimeFormatter.</li></ul></td>
        </tr>
        <tr>
            <td><h5>partition.timestamp-pattern</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>You can specify a pattern to get a timestamp from partitions. The formatter pattern is defined by 'partition.timestamp-formatter'.<ul><li>By default, read from the first field.</li><li>If the timestamp in the partition is a single field called 'dt', you can use '$dt'.</li><li>If it is spread across multiple fields for year, month, day, and hour, you can use '$year-$month-$day $hour:00:00'.</li><li>If the timestamp is in fields dt and hour, you can use '$dt $hour:00:00'.</li></ul></td>
        </tr>
        <tr>
            <td><h5>primary-key</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Define primary key by table options, cannot define primary key on DDL and table options at the same time.</td>
        </tr>
        <tr>
            <td><h5>read.batch-size</h5></td>
            <td style="word-wrap: break-word;">1024</td>
            <td>Integer</td>
            <td>Read batch size for orc and parquet.</td>
        </tr>
        <tr>
            <td><h5>record-level.expire-time</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>Record level expire time for primary key table, expiration happens in compaction, there is no strong guarantee to expire records in time. You must specific 'record-level.time-field' too.</td>
        </tr>
        <tr>
            <td><h5>record-level.time-field</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Time field for record level expire, it should be a seconds INT.</td>
        </tr>
        <tr>
            <td><h5>rowkind.field</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>The field that generates the row kind for primary key table, the row kind determines which data is '+I', '-U', '+U' or '-D'.</td>
        </tr>
        <tr>
            <td><h5>scan.bounded.watermark</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Long</td>
            <td>End condition "watermark" for bounded streaming mode. Stream reading will end when a larger watermark snapshot is encountered.</td>
        </tr>
        <tr>
            <td><h5>scan.file-creation-time-millis</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Long</td>
            <td>After configuring this time, only the data files created after this time will be read. It is independent of snapshots, but it is imprecise filtering (depending on whether or not compaction occurs).</td>
        </tr>
        <tr>
            <td><h5>scan.manifest.parallelism</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>The parallelism of scanning manifest files, default value is the size of cpu processor. Note: Scale-up this parameter will increase memory usage while scanning manifest files. We can consider downsize it when we encounter an out of memory exception while scanning</td>
        </tr>
        <tr>
            <td><h5>scan.max-splits-per-task</h5></td>
            <td style="word-wrap: break-word;">10</td>
            <td>Integer</td>
            <td>Max split size should be cached for one task while scanning. If splits size cached in enumerator are greater than tasks size multiply by this value, scanner will pause scanning.</td>
        </tr>
        <tr>
            <td><h5>scan.mode</h5></td>
            <td style="word-wrap: break-word;">default</td>
            <td><p>Enum</p></td>
            <td>Specify the scanning behavior of the source.<br /><br />Possible values:<ul><li>"default": Determines actual startup mode according to other table properties. If "scan.timestamp-millis" is set the actual startup mode will be "from-timestamp", and if "scan.snapshot-id" or "scan.tag-name" is set the actual startup mode will be "from-snapshot". Otherwise the actual startup mode will be "latest-full".</li><li>"latest-full": For streaming sources, produces the latest snapshot on the table upon first startup, and continue to read the latest changes. For batch sources, just produce the latest snapshot but does not read new changes.</li><li>"full": Deprecated. Same as "latest-full".</li><li>"latest": For streaming sources, continuously reads latest changes without producing a snapshot at the beginning. For batch sources, behaves the same as the "latest-full" startup mode.</li><li>"compacted-full": For streaming sources, produces a snapshot after the latest compaction on the table upon first startup, and continue to read the latest changes. For batch sources, just produce a snapshot after the latest compaction but does not read new changes. Snapshots of full compaction are picked when scheduled full-compaction is enabled.</li><li>"from-timestamp": For streaming sources, continuously reads changes starting from timestamp specified by "scan.timestamp-millis", without producing a snapshot at the beginning. For batch sources, produces a snapshot at timestamp specified by "scan.timestamp-millis" but does not read new changes.</li><li>"from-file-creation-time": For streaming and batch sources, produces a snapshot and filters the data files by creation time. For streaming sources, upon first startup, and continue to read the latest changes.</li><li>"from-snapshot": For streaming sources, continuously reads changes starting from snapshot specified by "scan.snapshot-id", without producing a snapshot at the beginning. For batch sources, produces a snapshot specified by "scan.snapshot-id" or "scan.tag-name" but does not read new changes.</li><li>"from-snapshot-full": For streaming sources, produces from snapshot specified by "scan.snapshot-id" on the table upon first startup, and continuously reads changes. For batch sources, produces a snapshot specified by "scan.snapshot-id" but does not read new changes.</li><li>"incremental": Read incremental changes between start and end snapshot or timestamp.</li></ul></td>
        </tr>
        <tr>
            <td><h5>scan.plan-sort-partition</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to sort plan files by partition fields, this allows you to read according to the partition order, even if your partition writes are out of order.<br />It is recommended that you use this for streaming read of the 'append-only' table. By default, streaming read will read the full snapshot first. In order to avoid the disorder reading for partitions, you can open this option.</td>
        </tr>
        <tr>
            <td><h5>scan.snapshot-id</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Long</td>
            <td>Optional snapshot id used in case of "from-snapshot" or "from-snapshot-full" scan mode</td>
        </tr>
        <tr>
            <td><h5>scan.tag-name</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Optional tag name used in case of "from-snapshot" scan mode.</td>
        </tr>
        <tr>
            <td><h5>scan.timestamp-millis</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Long</td>
            <td>Optional timestamp used in case of "from-timestamp" scan mode. If there is no snapshot earlier than this time, the earliest snapshot will be chosen.</td>
        </tr>
        <tr>
            <td><h5>scan.watermark</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Long</td>
            <td>Optional watermark used in case of "from-snapshot" scan mode. If there is no snapshot later than this watermark, will throw an exceptions.</td>
        </tr>
        <tr>
            <td><h5>sequence.field</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>The field that generates the sequence number for primary key table, the sequence number determines which data is the most recent.</td>
        </tr>
        <tr>
            <td><h5>sink.watermark-time-zone</h5></td>
            <td style="word-wrap: break-word;">"UTC"</td>
            <td>String</td>
            <td>The time zone to parse the long watermark value to TIMESTAMP value. The default value is 'UTC', which means the watermark is defined on TIMESTAMP column or not defined. If the watermark is defined on TIMESTAMP_LTZ column, the time zone of watermark is user configured time zone, the value should be the user configured local time zone. The option value is either a full name such as 'America/Los_Angeles', or a custom timezone id such as 'GMT-08:00'.</td>
        </tr>
        <tr>
            <td><h5>snapshot.expire.clean-empty-directories</h5></td>
            <td style="word-wrap: break-word;">true</td>
            <td>Boolean</td>
            <td>Whether to try to clean empty directories when expiring snapshots. Note that trying to clean directories might throw exceptions in filesystem, but in most cases it won't cause problems.</td>
        </tr>
        <tr>
            <td><h5>snapshot.expire.execution-mode</h5></td>
            <td style="word-wrap: break-word;">sync</td>
            <td><p>Enum</p></td>
            <td>Specifies the execution mode of expire.<br /><br />Possible values:<ul><li>"sync": Execute expire synchronously. If there are too many files, it may take a long time and block stream processing.</li><li>"async": Execute expire asynchronously. If the generation of snapshots is greater than the deletion, there will be a backlog of files.</li></ul></td>
        </tr>
        <tr>
            <td><h5>snapshot.expire.limit</h5></td>
            <td style="word-wrap: break-word;">10</td>
            <td>Integer</td>
            <td>The maximum number of snapshots allowed to expire at a time.</td>
        </tr>
        <tr>
            <td><h5>snapshot.num-retained.max</h5></td>
            <td style="word-wrap: break-word;">infinite</td>
            <td>Integer</td>
            <td>The maximum number of completed snapshots to retain. Should be greater than or equal to the minimum number.</td>
        </tr>
        <tr>
            <td><h5>snapshot.num-retained.min</h5></td>
            <td style="word-wrap: break-word;">10</td>
            <td>Integer</td>
            <td>The minimum number of completed snapshots to retain. Should be greater than or equal to 1.</td>
        </tr>
        <tr>
            <td><h5>snapshot.time-retained</h5></td>
            <td style="word-wrap: break-word;">1 h</td>
            <td>Duration</td>
            <td>The maximum time of completed snapshots to retain.</td>
        </tr>
        <tr>
            <td><h5>snapshot.watermark-idle-timeout</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>In watermarking, if a source remains idle beyond the specified timeout duration, it triggers snapshot advancement and facilitates tag creation.</td>
        </tr>
        <tr>
            <td><h5>sort-compaction.local-sample.magnification</h5></td>
            <td style="word-wrap: break-word;">1000</td>
            <td>Integer</td>
            <td>The magnification of local sample for sort-compaction.The size of local sample is sink parallelism * magnification.</td>
        </tr>
        <tr>
            <td><h5>sort-compaction.range-strategy</h5></td>
            <td style="word-wrap: break-word;">QUANTITY</td>
            <td><p>Enum</p></td>
            <td>The range strategy of sort compaction, the default value is quantity.
If the data size allocated for the sorting task is uneven,which may lead to performance bottlenecks, the config can be set to size.<br /><br />Possible values:<ul><li>"SIZE"</li><li>"QUANTITY"</li></ul></td>
        </tr>
        <tr>
            <td><h5>sort-engine</h5></td>
            <td style="word-wrap: break-word;">loser-tree</td>
            <td><p>Enum</p></td>
            <td>Specify the sort engine for table with primary key.<br /><br />Possible values:<ul><li>"min-heap": Use min-heap for multiway sorting.</li><li>"loser-tree": Use loser-tree for multiway sorting. Compared with heapsort, loser-tree has fewer comparisons and is more efficient.</li></ul></td>
        </tr>
        <tr>
            <td><h5>sort-spill-buffer-size</h5></td>
            <td style="word-wrap: break-word;">64 mb</td>
            <td>MemorySize</td>
            <td>Amount of data to spill records to disk in spilled sort.</td>
        </tr>
        <tr>
            <td><h5>sort-spill-threshold</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>If the maximum number of sort readers exceeds this value, a spill will be attempted. This prevents too many readers from consuming too much memory and causing OOM.</td>
        </tr>
        <tr>
            <td><h5>source.split.open-file-cost</h5></td>
            <td style="word-wrap: break-word;">4 mb</td>
            <td>MemorySize</td>
            <td>Open file cost of a source file. It is used to avoid reading too many files with a source split, which can be very slow.</td>
        </tr>
        <tr>
            <td><h5>source.split.target-size</h5></td>
            <td style="word-wrap: break-word;">128 mb</td>
            <td>MemorySize</td>
            <td>Target size of a source split when scanning a bucket.</td>
        </tr>
        <tr>
            <td><h5>spill-compression</h5></td>
            <td style="word-wrap: break-word;">"LZ4"</td>
            <td>String</td>
            <td>Compression for spill, currently lz4, lzo and zstd are supported.</td>
        </tr>
        <tr>
            <td><h5>streaming-read-mode</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td><p>Enum</p></td>
            <td>The mode of streaming read that specifies to read the data of table file or log<br /><br />Possible values:<br /><ul><li>file: Reads from the data of table file store.</li></ul><ul><li>log: Read from the data of table log store.</li></ul><br /><br />Possible values:<ul><li>"log": Reads from the log store.</li><li>"file": Reads from the file store.</li></ul></td>
        </tr>
        <tr>
            <td><h5>streaming-read-overwrite</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>Whether to read the changes from overwrite in streaming mode. Cannot be set to true when changelog producer is full-compaction or lookup because it will read duplicated changes.</td>
        </tr>
        <tr>
            <td><h5>tag.automatic-creation</h5></td>
            <td style="word-wrap: break-word;">none</td>
            <td><p>Enum</p></td>
            <td>Whether to create tag automatically. And how to generate tags.<br /><br />Possible values:<ul><li>"none": No automatically created tags.</li><li>"process-time": Based on the time of the machine, create TAG once the processing time passes period time plus delay.</li><li>"watermark": Based on the watermark of the input, create TAG once the watermark passes period time plus delay.</li><li>"batch": In the batch processing scenario, the tag corresponding to the current snapshot is generated after the task is completed.</li></ul></td>
        </tr>
        <tr>
            <td><h5>tag.callback.#.param</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>Parameter string for the constructor of class #. Callback class should parse the parameter by itself.</td>
        </tr>
        <tr>
            <td><h5>tag.callbacks</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>String</td>
            <td>A list of commit callback classes to be called after a successful tag. Class names are connected with comma (example: com.test.CallbackA,com.sample.CallbackB).</td>
        </tr>
        <tr>
            <td><h5>tag.creation-delay</h5></td>
            <td style="word-wrap: break-word;">0 ms</td>
            <td>Duration</td>
            <td>How long is the delay after the period ends before creating a tag. This can allow some late data to enter the Tag.</td>
        </tr>
        <tr>
            <td><h5>tag.creation-period</h5></td>
            <td style="word-wrap: break-word;">daily</td>
            <td><p>Enum</p></td>
            <td>What frequency is used to generate tags.<br /><br />Possible values:<ul><li>"daily": Generate a tag every day.</li><li>"hourly": Generate a tag every hour.</li><li>"two-hours": Generate a tag every two hours.</li></ul></td>
        </tr>
        <tr>
            <td><h5>tag.default-time-retained</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Duration</td>
            <td>The default maximum time retained for newly created tags.</td>
        </tr>
        <tr>
            <td><h5>tag.num-retained-max</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Integer</td>
            <td>The maximum number of tags to retain.</td>
        </tr>
        <tr>
            <td><h5>tag.period-formatter</h5></td>
            <td style="word-wrap: break-word;">with_dashes</td>
            <td><p>Enum</p></td>
            <td>The date format for tag periods.<br /><br />Possible values:<ul><li>"with_dashes": Dates and hours with dashes, e.g., 'yyyy-MM-dd HH'</li><li>"without_dashes": Dates and hours without dashes, e.g., 'yyyyMMdd HH'</li></ul></td>
        </tr>
        <tr>
            <td><h5>target-file-size</h5></td>
            <td style="word-wrap: break-word;">128 mb</td>
            <td>MemorySize</td>
            <td>Target size of a file.</td>
        </tr>
        <tr>
            <td><h5>write-buffer-for-append</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>This option only works for append-only table. Whether the write use write buffer to avoid out-of-memory error.</td>
        </tr>
        <tr>
            <td><h5>write-buffer-size</h5></td>
            <td style="word-wrap: break-word;">256 mb</td>
            <td>MemorySize</td>
            <td>Amount of data to build up in memory before converting to a sorted on-disk file.</td>
        </tr>
        <tr>
            <td><h5>write-buffer-spill.max-disk-size</h5></td>
            <td style="word-wrap: break-word;">infinite</td>
            <td>MemorySize</td>
            <td>The max disk to use for write buffer spill. This only work when the write buffer spill is enabled</td>
        </tr>
        <tr>
            <td><h5>write-buffer-spillable</h5></td>
            <td style="word-wrap: break-word;">(none)</td>
            <td>Boolean</td>
            <td>Whether the write buffer can be spillable. Enabled by default when using object storage.</td>
        </tr>
        <tr>
            <td><h5>write-manifest-cache</h5></td>
            <td style="word-wrap: break-word;">0 bytes</td>
            <td>MemorySize</td>
            <td>Cache size for reading manifest files for write initialization.</td>
        </tr>
        <tr>
            <td><h5>write-max-writers-to-spill</h5></td>
            <td style="word-wrap: break-word;">5</td>
            <td>Integer</td>
            <td>When in batch append inserting, if the writer number is greater than this option, we open the buffer cache and spill function to avoid out-of-memory. </td>
        </tr>
        <tr>
            <td><h5>write-only</h5></td>
            <td style="word-wrap: break-word;">false</td>
            <td>Boolean</td>
            <td>If set to true, compactions and snapshot expiration will be skipped. This option is used along with dedicated compact jobs.</td>
        </tr>
        <tr>
            <td><h5>zorder.var-length-contribution</h5></td>
            <td style="word-wrap: break-word;">8</td>
            <td>Integer</td>
            <td>The bytes of types (CHAR, VARCHAR, BINARY, VARBINARY) devote to the zorder sort.</td>
        </tr>
    </tbody>
</table>
